Fix OGNL null pointer exception in condition expression evaluation #3132
+196
−0
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
OGNL 3.3.5 throws
source is null for getProperty(null, "X")when expressions access properties on null objects (e.g.,params[2].fieldwhereparams[2]is null). This crashes TimeTunnel and other commands using condition expressions.Changes
OgnlExpress.get(): Catch
OgnlExceptioncontaining "source is null for getProperty" and return null instead of propagating. Provides null-safe navigation similar to optional chaining.Tests: Added unit and integration tests covering null property access, null array indexing, and realistic Advice scenarios with null params/returnObj.
Example
Condition expressions like
params[2] != null && params[2].field == "value"now evaluate correctly instead of crashing on the first null access.Original prompt
💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.